5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
- Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-2: Getting Started

Frame/Image Positioning


When you create frames and images for menu, input, and output processes, you are asked to define a size and display position for each.

Sizes are stated in terms of the number of rows and columns a frame or image occupies. It is important to note that, while images consume physical space on the screen or printed page, frames do not. Frames simply designate regions for image placement.

The position a frame or image occupies (where it displays on the screen or page) is determined by a number of factors, including the type of process, the way the process was invoked, and whether or not it includes a scrolling display.

You can surround frames and/or images in menu or input processes with a box. Boxes do not consume rows or columns within the space that is defined for a frame. They do, however, consume more physical space than overlines and underlines. The physical space on a screen that is consumed by a box is system-specific.

Various factors affect the actual positioning of a frame or image, as discussed in the following sections:

Screen Positioning

The Effect of Child Invocation Screen Display

Page Positioning

The Effect of Scrolling Frames on Screen and Page Positioning

Application Design Manual                                         "Powered by Appx Software"

261

©2006 By APPX Software, Inc. All Rights Reserved